Repository navigation
fix(release): tag and release even when npm is slow to serve a package - #66
Merged
Merged
Conversation
`npm publish` had succeeded for every package, but the registry took longer than the five-minute wait to serve one (@cloudhal/cli in 0.3.8, @cloudhal/schedules in 0.3.10). The script threw, so the tag and the GitHub Release were skipped until a re-run (with a second approval). A package that npm accepted is published; the slow one is now a warning. Co-Authored-By: Claude Opus 5.5 <[email protected]> Signed-off-by: Madraka <[email protected]>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Twice now (0.3.8:
@cloudhal/cli, 0.3.10:@cloudhal/schedules) everynpm publishsucceeded but the registry took more than the 5-minute wait to serve one package.publish-ci.tsthrewnpm does not serve yet, so thevX.Y.Ztag and the GitHub Release were skipped until the job was re-run (with a secondnpm-publishapproval).A package npm accepted is published; the wait stays, and a package still not served after it is logged as a warning instead of failing the release.
No changeset:
scripts/is not published.🤖 Generated with Claude Code